home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Internet
/
Collection of Internet.iso
/
infosrvr
/
dev
/
www_talk.930
/
000893_timbl@www3.cern.ch _Thu Apr 15 09:23:56 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-01-24
|
3KB
Return-Path: <timbl@www3.cern.ch>
Received: from dxmint.cern.ch by nxoc01.cern.ch (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
id AA20023; Thu, 15 Apr 93 09:23:56 MET DST
Received: from www3.cern.ch by dxmint.cern.ch (5.65/DEC-Ultrix/4.3)
id AA04192; Thu, 15 Apr 1993 09:43:31 +0200
Received: by www3.cern.ch (NX5.67c/NX3.0S)
id AA06587; Thu, 15 Apr 93 09:41:14 +0100
Date: Thu, 15 Apr 93 09:41:14 +0100
From: Tim Berners-Lee <timbl@www3.cern.ch>
Message-Id: <9304150841.AA06587@www3.cern.ch>
Received: by NeXT.Mailer (1.87.1)
Received: by NeXT Mailer (1.87.1)
To: marca@ncsa.uiuc.edu (Marc Andreessen)
Subject: Re: Project Gutenberg's Roget's Thesaurus
Cc: www-talk@nxoc01.cern.ch
Reply-To: timbl@nxoc01.cern.ch
| Date: Tue, 13 Apr 93 12:42:01 -0500
| From: marca@ncsa.uiuc.edu (Marc Andreessen)
| Guido.van.Rossum@cwi.nl writes:
[...]
| > I see a problem coming here: how does an unreplicated document
(say my
| > own home page) mane a reference to such a replicated document?
If I
| > have a reference to the closest replica, a user far away who
follows
| > such a link will get pointed to the replica closest to *me*, not
| > closest to her.
| >
| > Some possible solutions:
| >
| > - a translation scheme whereby clients "know" (e.g. from a local
| > configuration file that may be updated automatically as mirror
sites
| > are added) that information at host X is identical to info at
host Y
Yes, this is possible with the 2.0 library. The line mode client
doesn't have the command line option yet, but the client library
can use a rule file, just like a server.
| > - a magic string in hostnames that is translated dependent on the
| > geographical position of the client (e.g.
| > http://info-cern.closestmirror/...)
This has been discussed, in fact having a host name which translates
info many IP addresses -- all the apparatus is there already in DNS
and most people say it won't break anything, we just need code to, if
DNS returns >1 IP address, ping them all to get the closest and
remember which one it is.
| > - upon first contact with a server, it might respond with "please
| > try the following mirror site which is closer to you" (this could
be
| > put in HTTP2 I suppose).
This is already the HTTP2 spec. The reply field can be a "forward"
reply containing a pointer to the real object. That is, HTTP2
servers can be used as name servers. No code yet in the library.
See http://info.cern.ch/hypertext/WWW/Protocols/HTTP/HTRESP.html#z9
| > This is a real problem with embedding location information in
URLs...
|
| Sounds like it's time to move URN's (or whatever persistent
Internet
| resource identifiers are being called these days) out of the theory
| stage and into practice.... anyone know what the status of the URN
| work that was/is apparently going somewhere in the IETF?
I thought it was going to get closer, but basically it was agreed
that the format urn:publisher/id would work with a finite number of
publishers. I think you might see Peter Deutch and Chis Weider maybe
putting some code together???
Remember that if you have to contact a name server every time,
you slow things down anyway. Basically, a little common sense
in the client would guess that a related document was avalable from
the same server as last time.
Tim